Real-time dvr programming

ABSTRACT

Techniques for real-time DVR programming employ secure instant message protocol in a DVR environment. An embodiment sends an instant message to the DVR which causes the DVR to open a new secure connection with the service provider for synchronizing data on the DVR with updated programming data from the service provider. Another embodiment uses an already established connection with an instant message server for synchronizing data on the DVR with updated programming data from the service provider.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims benefit as a Continuation of U.S. patentapplication Ser. No. 12/347,897, filed Dec. 31, 2008, under 35 U.S.C.§120. The above-mentioned patent applications are assigned to theassignee of the present application and are hereby incorporated byreference as if fully set forth herein. The applicant(s) hereby rescindany disclaimer of claim scope in the parent application(s) or theprosecution history thereof and advise the USPTO that the claims in thisapplication may be broader than any claim in the parent application(s).

FIELD OF TECHNOLOGY

The present invention relates to digital video recorders (“DVRs”). Theinvention relates more specifically to a real-time DVR usage andreporting system.

BACKGROUND

The approaches described in this section are approaches that could bepursued, but not necessarily approaches that have been previouslyconceived or pursued. Therefore, unless otherwise indicated, it shouldnot be assumed that any of the approaches described in this sectionqualify as prior art merely by virtue of their inclusion in thissection.

The introduction of the Digital Video Recorder (DVR) to the consumerworld has revolutionized the way viewers watch and record televisionprograms. DVRs eliminate the complications of VCRs and the need forvideo tapes. DVRs record television programs on a hard drive that iscapable of storing a large number of television programs. Because DVRsare usually box-like in shape, and are often found sitting on top of thetelevision sets to which they are connected, DVRs typically are includedin the broad category of devices now called “set-top boxes.” Much likeVCRs, DVRs receive one or more television signals as input from cablesor satellite dishes, (or, in some cases, unlike VCRs, from broadbandnetwork connections) and also output television signals to a televisionset or other display.

At least one such DVR automatically records several television programsin advance of the time that a user will watch those television programs.After one or more television programs have been recorded and stored on ahard drive, the DVR presents, to the user, through the television set, auser interface that identifies the television programs which currentlyare available for viewing. This user interface comprises a menu thatallows the user to select, using a remote control device for the DVR,one of the currently recorded television programs. In DVRs produced byTiVo Inc., this menu is often called the “now playing” menu.

After a user selects a recorded television program, the DVR plays theselected television program to the user by reading the appropriatedigital recording from the hard drive and sending a corresponding signalto the television set. While the television program is being played tothe user, the DVR also receives signals from the user's remote control.Through the remote control, a user may instruct the DVR to performvarious operations relative to the television program. For example, theuser may instruct the DVR to play the television program backward for adesired period of time (“rewind”). The user may play the televisionprogram forward with greater than usual speed (“fast forward”). The usermay play the television program forward with slower than usual speed.The user may cause the currently displayed video frame of the televisionprogram to be displayed indefinitely (“pause”), or stop the playing ofthe television program entirely. In this manner, the user may temporallytraverse the television program however the user likes.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is illustrated by way of example, and not by wayof limitation, in the figures of the accompanying drawings and in whichlike reference numerals refer to similar elements and in which:

FIG. 1A is a block diagram illustrating a network with content andservice providers for a DVR, according to a possible embodiment;

FIG. 1B is a block diagram illustrating a general overview of thecomponents of a Digital Video Recorder (DVR), according to a possibleembodiment;

FIG. 2A is a block diagram illustrating service provider comprising anXMPP server internally, according to a possible embodiment;

FIG. 2B is a block diagram illustrating XMPP server residing externallyto service provider, according to a possible embodiment;

FIG. 3A is a flow diagram showing an example DVR/service providersynchronization process flow, according to a possible embodiment;

FIG. 3B is a flow diagram showing an example DVR/service providersynchronization process flow, according to a possible embodiment;

FIG. 3C is a flow diagram showing an example of direct communicationfrom a device to a DVR, according to a possible embodiment; and

FIG. 4 is a block diagram that illustrates a computer system upon whicha possible embodiment may be implemented.

DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS

A method and apparatus for real-time DVR programming is described. Inthe following description, for the purposes of explanation, numerousdetails are set forth in order to provide a thorough understanding ofthe present invention. It will be apparent, however, that the presentinvention may be practiced without such details. In other instances,well-known structures and devices are shown in block diagram form inorder to avoid unnecessarily obscuring the present invention.

STRUCTURAL OVERVIEW

FIG. 1A illustrates a network with content and service providers for aDVR, according to a possible embodiment. The system comprises DVR 102which is in communication with network 105 through any communicationinterface, such as an Ethernet interface or wireless communicationsport. The functionality of a DVR is typified in U.S. Pat. No. 6,233,389which is owned by the Applicants and is hereby incorporated byreference. The system also includes service provider server (“serviceprovider”) 104, storage 106 for service provider 104, content provider108, personal computer 110 and portable device 112.

Personal computer 110 may be a personal computing device, such as adesktop computer or laptop computer, and is also in communication withnetwork 105 through any communications interface, including wireless.Portable device 112 may be any handheld computing device, cellularphone, portable media player, or any other portable device capable ofdisplaying or playing multimedia content and is also in communicationwith network 105 through any communications interface, includingwireless. DVR 102, personal computer 110, and portable device 112 eachcommunicate as client with service provider server 104 through network105. In a possible embodiment, DVR 102, personal computer 110, andportable device 112 each communicate with content provider 110 throughnetwork 105. Storage 106 may be internal to service provider 104 (notshown) or external to service provider 104 as shown.

Network 105 may be implemented by any medium or mechanism that providesfor the exchange of data between devices in the communication system.Examples of network 105 include, without limitation, a network such as aLocal Area Network (LAN), Wide Area Network (WAN), the Internet, one ormore terrestrial, satellite, or wireless links, etc. Alternatively oradditionally, any number of devices connected to network 105 may also bedirectly connected to each other through a communications link.

In a possible embodiment, content provider 108 provides broadcastprogram content to DVR 102 via cable, satellite, terrestrialcommunication, or other transmission method. Broadcast program contentmay include any multimedia content such as: audio, image, or videocontent. In a possible embodiment, content provider 108 providesmultimedia content, such as any downloadable content, through network105 to DVR 102, personal computer 110, or portable device 112.

In a possible embodiment, DVR 102 communicates with service provider 104and storage 106, which provide program guide data, graphical resources(such as fonts, pictures, etc.), service information, software,advertisements, event identification data, and other forms of data thatenable DVR 102 to operate independently of service provider 104 tosatisfy user interests.

In a possible embodiment, content provider 108 may provide, to serviceprovider 104, content data and/or any metadata, including promotionaldata, icons, web data, and other information. Service provider 104 maythen interpret the metadata and provide the content data and/or metadatato DVR 102, personal computer 110, or portable device 112.

Referring to FIG. 1B, in a possible embodiment, DVR 102 generallycomprises one or more components, signified by signal converter 154,that may be used to digitize an analog television signal and convert itinto a digital data stream or accept a digital data stream. An exampleof the internal structure and operation of a DVR is further described inU.S. Pat. No. 6,233,389.

DVR 102 receives broadcast signals from an antenna, from a cable TVsystem, satellite receiver, etc., via input 152A. Input 152A maycomprise one or more tuning modules that allow one or more signals to bereceived and recorded simultaneously. For example, a TV input streamreceived by input 152A may take the form of a National TelevisionStandards Committee (NTSC) compliant signal or a Phase Alternating Line(PAL) compliant broadcast signal. For another example, a TV input streamreceived by input 152A may take a digital form such as a DigitalSatellite System (DSS) compliant signal, a Digital Broadcast Services(DBS) compliant signal, or an Advanced Television Standards Committee(ATSC) compliant signal. DBS, DSS, and ATSC are based on standardscalled Moving Pictures Experts Group 2 (MPEG-2) and MPEG-2 Transport.MPEG-2 Transport is a standard for formatting the digital data streamfrom the TV source transmitter so that a TV receiver can disassemble theinput stream to find programs in the multiplexed signal.

An MPEG-2 transport multiplex supports multiple programs in the samebroadcast channel with multiple video and audio feeds and private data.Input 152A tunes to a particular program in a channel, extracts aspecified MPEG stream from the channel, and feeds the MPEG stream to therest of the system. Analog TV signals are encoded into a similar MPEGformat using separate video and audio encoders, such that the remainderof the system is unaware of how the signal was obtained. Information maybe modulated into the vertical blanking interval (VBI) of the analog TVsignal in a number of standard ways; for example, the North AmericanBroadcast Teletext Standard (NABTS) may be used to modulate informationonto certain lines of an NTSC signal, which the FCC mandates the use ofa certain other line for closed caption (CC) and extended data services(EDS). Such signals are decoded by input 152A and passed to the othermodules as if the signals had been delivered via an MPEG-2 private datachannel.

Recording module 160 records the incoming data stream by storing thedigital data stream on at least one storage facility, signified bystorage 164A/164B that is designed to retain segments of the digitaldata stream. Storage 164A/164B may be one or more non-volatile storagedevices (e.g., hard disk, solid state drive, USB external hard drive,USB external memory stick, USB external solid state drive, networkaccessible storage device, etc.) that are internal 164A and/or external164B. A signal converter 154 retrieves segments of the data stream,converts the data stream into an analog signal, and then modulates thesignal onto a RF carrier, via output 152B, through which the signal isdelivered to a standard TV set. Output 152B may alternatively deliver adigital signal to a TV set or video monitor with signal converter 154,converting the data stream into an appropriate digital signal. Forexample, DVR 102 may utilize a High-Definition Multimedia Interface(HDMI) for sending digital signals to a TV via a HDMI cable.

DVR 102 also includes a communication interface 162, through which theDVR 102 communicates with network 105 via Ethernet, wireless network,modem, or other communications standard. Further, DVR 102 may beintegrated into a TV system such that the components described above arehoused in a TV set capable of performing the functions of each componentof DVR 102.

In another embodiment, DVR 102 generally comprises one or morecomponents necessary to receive, record, store, transfer and playbackdigital data signals from one or more sources, such as a PC, a DVR, aservice provider, or content server. DVR 102 can transfer digital datasignals to another DVR, PC, or any other suitably configured device,such as a handheld device or cell phone, etc. DVR 102 may encode ordecode digital signals via encoder 156A and decoder 156B into one ormore formats for playback, storage or transfer. According to a possibleembodiment, encoder 156A produces MPEG streams. According to anotherembodiment, encoder 156A produces streams that are encoded using adifferent codec. Decoder 156B decodes the streams encoded by encoder156A or streams that are stored in the format in which the streams werereceived using an appropriate decoder. DVR 102 can also encrypt ordecrypt digital data signals using encryptor/decryptor 158 for storage,transfer or playback of the digital data signals.

In a possible embodiment, DVR 102 communicates with service provider104, which provides program guide data, graphical resources such asbrand icons and pictures, service information, software programs,advertisements, and other forms of data that enable DVR 102 to operateindependently of the service provider 104 to perform autonomousrecording functions. Communication between DVR 102 and service provider104 may use a secure distribution architecture to transfer data betweenthe DVR 102 and the service provider 104 such that both the service dataand the user's privacy are protected.

DVR SYNCHRONIZATION WITH SERVICE PROVIDER BY POLLING

A possible embodiment of DVR synchronization with service provider 104by polling may be described with respect to FIG. 1A and FIG. 1B. Storage164A/164B of DVR 102 comprises program guide data, season pass data,wishlist data, now playing data, to do data (e.g., what programs arescheduled), suggestions data, etc. A season pass is a type of recordingthat keeps track of episodes of a television series. For example, theservice provided by TiVo (TiVo Inc., Alviso, Calif.) records episodes ofthe television series every week, even when the day or time of a showingof an episode changes. Via a season pass, a user may indicate how manyepisodes to store and whether or not to store reruns. A wishlist is alist of one or more content items that a user desires to record orschedule to record to the user's DVR when the content item becomesavailable. The wishlist is specified using any type of information suchas an actor's name, director's name, movie title, etc. The DVR 102records a show or movie that meets the wishlist specification whenever ashow or movie is broadcast or is available for download via a network,such as the Internet, intranet, etc. Storage 106 of service provider 104also comprises a copy of such data for DVR 102. For example, storage 106comprises one or more databases, which comprise tables that areassociated with DVR 102. As well, storage 106 comprises copies of allother DVR clients (e.g., as data stored in tables associated with eachof the other DVR clients), which service provider 104 supports and withwhich service provider 104 communicates (not shown.) DVR 102periodically establishes a Secure Sockets Layer (SSL) connection to andcontacts (“polls”) service provider 104 to initiate synchronizationbetween data stored in storage 164A/164B of DVR 102 and data stored instorage 106 of service provider 104. Synchronization between data storedin storage 164A/164B of DVR 102 and data stored in storage 106 ofservice provider 104 as used herein means causing at least a portion ofdata stored in storage 164A/164B and at least a portion of data storedin storage 106 to represent the same content. For example, in a possibleembodiment, DVR 102 contacts service provider 104 via network 105 tosynchronize every fifteen minutes. In a possible embodiment,synchronization is achieved by DVR 102 contacting service provider 104and sending a subset of local data in storage 164A/164B, e.g., data thatreflects updates to the local data stored in storage 164A/164B, toservice provider 104 that stores the data on storage 106. In anotherexample, a viewer, from the viewer's PC 110, adds a new season pass fora series, such as The War, to the viewer's collection of season passes.In this example, the viewer, from the viewer's PC 110, adds the newseason pass for the series by causing PC 110 to send data related toadding the season pass to service provider 104, which then stores thedata in the appropriate table(s) associated with the viewer's DVR 102 inthe database on storage 106. When DVR 102 initiates synchronizing datawith service provider 104, data reflecting the newly added season passcontained in storage 106 is sent to DVR 102. It should be appreciatedthat DVR/service provider synchronization is not limited by whichelement (e.g., DVR 102 or service provider 104) initiatessynchronization and sends updated data to the receiving element. Forexample, DVR 102 may initiate synchronization or service provider 104may initiate synchronization.

An example DVR/service provider synchronization process is as follows. Auser is logged onto the Internet (e.g., network 105) using personalcomputer 110. For example, the user is navigating the TiVo Central™Online web page via his browser and, from the TiVo Central Online remotescheduling facility, schedules a program to record on the user's DVR102. The message to record the program gets sent from the web pageinterface on personal computer 110 to service provider 104. The programinformation is added to the database tables associated with the user'sDVR 102 by service provider 104, e.g., on storage 106 comprising datathat represents the schedule of programs for user's DVR 102. The nexttime that DVR 102 and service provider 104 synchronize data, datareflecting the schedule with the added program is sent by serviceprovider 104 from storage 106 to DVR storage 164A/164B. DVR 102 is thusconfigured to record the added program according to the user's request.

INSTANT MESSAGE PROTOCOL

In a possible embodiment, DVR 102, personal computer 110, portabledevice 112, or any other appropriately configured device, maycommunicate with service provider 104 on network 105 using a secureclient-server instant message protocol to transfer data between DVR 102,personal computer 110, portable device 112, or any other appropriatelyconfigured device and service provider 104 such that both the servicedata and the user's privacy are protected. In a possible embodiment,data may be transferred using secure client-server instant messagecommunications protocol over network 105 via wired, wireless, or anyother communication interface. In a possible embodiment, DVR 102receives and sends instant messages through communication interface 162.As an example, on a cell phone, a user might select a program to berecorded and the request to record the program is sent as an instantmessage to service provider 104. Instant message communication betweenDVR 102, personal computer 110, or portable device 112 and serviceprovider 104 may be described with reference to FIG. 2A and FIG. 2B.FIG. 2A is a block diagram of service provider 104 comprising anExtensible Messaging and Presence Protocol (XMPP) server 202 internally.In a possible embodiment, XMPP server 202 is communicatively connectedto network 105 and external to service provider 104, as shown in FIG.2B. It should be appreciated that in a possible embodiment, any systemconfigured for instant message communications protocol may becontemplated and that any embodiment described herein using XMPP ismeant by way of example and is not meant to be limiting. For example AOLInstant Messenger (AIM®), Microsoft's Windows Live, ICQ®, or ShortMessaging Services (SMS) are each a system that may be used for instantmessage communications protocol in accordance with one or moreembodiments. In a possible embodiment, commands from any of DVR 102,personal computer 110, or portable device 112 are sent via network 105to service provider 104 as instant messages. After receipt of suchinstant messages, service provider 104 updates appropriate databasetables in storage 106 that are associated with the user associated withthe command. As an example, in a possible embodiment, after receipt ofone or more instant messages containing information relating to aparticular update to a user's DVR, service provider 104 updatesappropriate database objects in central site database 100, as describedin the commonly owned U.S. Pat. No. 6,728,713, titled, “DistributedDatabase Management System,” dated Apr. 27, 2004, which is incorporatedherein in its entirety as if fully set forth herein. It should beappreciated that such configurations are by way of example only and arenot meant to be limiting.

In a possible embodiment, XMPP is an open source protocol for real-timeextensible instant messaging (IM) over a network as well as presenceinformation, such as used for buddy lists. XMPP is based on openstandards, similar to email. Similar to a user in an open emailenvironment, a user in an open XMPP environment with a domain name and asuitable Internet connection may run an XMPP server and communicatedirectly with users on other XMPP servers. An example client XMPPapplication is Google Talk. Google Talk is a Windows application forVoice over IP and instant messaging, offered by Google, Mountain View,Calif.

An example XMPP message delivery process from UserA to UserB is asfollows. UserA sends a message intended for UserB to UserA's XMPPserver. If UserB is blocked on UserA's server, then the message isdropped. Otherwise, UserA's XMPP server opens a connection to UserB'sXMPP server. A possible embodiment of the opened connection may includeobtaining authorization and obtaining an encrypted connection. After theconnection is established, UserB's XMPP server checks if UserA isblocked on UserB's XMPP server. If UserA is blocked on UserB's XMPPserver, the message is dropped. In a possible embodiment, if UserB isnot presently connected to UserB's XMPP server, the message is storedfor later delivery. It should be appreciated that other options apply,such as dropping the message. In a possible embodiment, if UserB ispresently connected to UserB's XMPP server, the message is delivered toUserB. It should be appreciated that in a possible embodiment, UserA'sserver and UserB's server are the same server. For instance, UserA sendsinstant messages to UserB and receives instant messages from UserB bysending messages to and receiving messages from an XMPP server and UserBsends instant messages to UserA and receives messages from UserA bysending messages to and receiving messages from the XMPP server.

Further details on example structure and functionality of XMPP may befound in The Internet Society's “Request For Comment” (RFC) documentsRFC3920, “Extensible Messaging and Presence Protocol: Core” and RFC3921,“Extensible Messaging and Presence Protocol: Instant Messaging andPresence.”

INSTANT MESSAGE SYNCHRONIZATION

In a possible embodiment, DVR 102 is an instant messaging client andhosts an instant message client application. DVR 102 attempts tomaintain an instant messaging connection with instant message XMPPserver 202 at all times. Service provider 104 is also an instantmessaging client and hosts an instant message client application. Aswell, service provider 104 attempts to maintain an instant messagingconnection with instant message XMPP server 202 at all times. In apossible embodiment, DVR 202, XMPP server 202, and service provider 104communicate according to open standard XMPP protocol, e.g., as describedabove. In a possible embodiment, service provider 104 comprises relatedsoftware that enables service provider 104 to communicate with storage106. It should be appreciated that in certain contexts herein,references to service provider 104 are used in the collective sense andare meant to include reference to the related software that managesstorage 106.

A possible embodiment of instant message synchronization may bedescribed with reference to FIG. 3A. FIG. 3A is a flow diagram showingan example DVR/service provider synchronization process flow. Thisexample synchronization process flow begins with a user remotelyrequesting a programming event, e.g., to add a program, via serviceprovider 104 (Step 302.) For example, PC 110 may request to add aprogram to the user's schedule of recordings for DVR 102. For example,through PC 110 the user may remotely add a program to record using TiVoCentral Online through service provider 104. Service provider 104updates database tables on storage 106 that are associated with theuser's DVR to include the program (Step 304.) As well, service provider104 sends an instant message to DVR 102 via XMPP server 202 (Step 306.)It should be appreciated that, in a possible embodiment, DVR 102attempts to maintain the connection to XMPP server 202 at all times,reconnecting automatically whenever the connection drops. Similarly, itshould be appreciated that, in a possible embodiment, service provider104 attempts to maintain the connection to XMPP server 202 at all times,reconnecting automatically whenever the connection drops. In eithercase, when the connection to XMPP server 202 is not up for any reason,the instant message is discarded. In the example, the instant messageinforms DVR 102 that a change has been made to the database tables thatare associated with the user's DVR in storage 106 and requests that DVR102 synchronize data in storage 164A/164B with data in storage 106. In apossible embodiment, the notification causes DVR 102 to open a new SSLconnection with service provider 104 specifically for thesynchronization process and to close the newly opened SSL connectionwhen the synchronization of the relevant data in storage 106 with datain storage 164A/164B is done (Step 308.) It should be appreciated thatcertain details in the example are by way of illustration only and arenot meant to be limiting. As an example, while a remote user requests achange, the request for change may be sent from any configurable device,such as portable device 112.

Another embodiment of DVR/service provider synchronization may bedescribed with reference to FIG. 3B. FIG. 3B is a flow diagram showingan example DVR/service provider synchronization process flow that issimilar to FIG. 3A, however with a different last step. As in FIG. 3A,the example synchronization process flow of FIG. 3B begins with a userremotely requesting a programming event, e.g., to add a program, viaservice provider 104 (Step 302.) For example, PC 110 requests theservice to add a program to the user's schedule of recordings for DVR102. For example, through PC 110 the user may remotely add a programusing TiVo Central™ Online through service provider 104. Serviceprovider 104 updates database tables on storage 106 that are associatedwith the user's DVR to include the program (Step 304.) As well, serviceprovider 104 sends an instant message to DVR 102 via XMPP server 202(Step 306.) It should be appreciated that, in a possible embodiment, DVR102 attempts to maintain the connection to XMPP server 202 at all times,reconnecting automatically whenever the connection drops. Similarly, itshould be appreciated that, in a possible embodiment, service provider104 attempts to maintain the connection to XMPP server 202 at all times,reconnecting automatically whenever the connection drops. In eithercase, when the connection to XMPP server 202 is not up for any reason,the instant message is discarded. In the example, the instant messageinforms DVR 102 that a change has been made to the database tables thatare associated with the user's DVR in storage 106 and requests that DVR102 synchronize data in storage 164A/164B with data in storage 106.Responsive to the message, DVR 102 uses the already establishedconnection with XMPP server 202 to pass and/or receive thesynchronization data to synchronize data in storage 164A/164B with datain storage 106 (Step 310.) It should be appreciated that certain detailsin the example are by way of illustration only and are not meant to belimiting. For instance, while, in the example, a remote user requests achange from PC 110, in another possible embodiment, the request forchange may be sent from any configurable device, such as portable device112. It should be appreciated that this approach allows for fast updatesof DVR 102. A user may be able to request to record a multimedia contenta minute or two before the multimedia content begins and DVR 102 may beupdated and record the multimedia content without missing any of thecontent material.

It should be appreciated that client-server instant message protocol ina DVR environment is not limited to synchronizing schedule-related andrecording-related data. Indeed, any type of data stored in storage 106of service provider 104 may be synchronized with data stored in DVRstorage 164A/164B, such as software, electronic program guide data,advertisements, multimedia content, etc. As well, any type of datastored in DVR storage 164A/164B may be synchronized with data stored instorage 106 of service provider 104.

As well, through an instant message connection, data reflecting any typeof activity from any client may be sent to the service provider storageon a real-time basis. The type of and use of such gathered data islimitless. For example, the data may be aggregated and analyzed formarketing or towards providing better customer service. As anotherexample, data gathered for a particular user may be used to initiate acustomized or targeted process for that particular user, and so forth.

Real-Time Direct Communication Between Device and DVR

In a possible embodiment, a device, such as, for example, portabledevice 112, is in direct communication, via an instant message server,with a DVR, such as DVR 102. In a possible embodiment, the device(“direct device”) is configured with customized user interface DVRsoftware (“DVR UI”) that allows the user to program the user's DVR fromthe direct device as though the user is operating the user's DVR athome, the office, or any place where the DVR is located. Further, thedirect device hosts an instant message client application such that thedirect device is an instant messaging client. This approach allows forfast updates to the user's DVR from a direct device, such as a cellphone.

A possible embodiment can be described with reference to FIG. 3C, a flowdiagram showing an example of direct communication from a device to aDVR. In an example implementation, a user desires to request aprogramming event, such as to add a season pass for a particulartelevision program, from the user's cell phone. In a possibleembodiment, the user opens his cell phone and from the cell phonelaunches his copy of the DVR UI. While the DVR UI is running, the usernavigates to the appropriate screen and enters a command to add theseason pass (Step 320.) After receiving the command, the DVR UI causes acorresponding instant message to be created that is to be delivered tothe user's DVR (Step 322.) In a possible embodiment, the DVR UIgenerates the instant message and provides it to the instant messageclient application or, in another possible embodiment, the instantmessage client application generates the instant message. The instantmessage contains data that causes the user's DVR to add the season pass,for example, as though the user was at home and operating his DVR. Itshould be appreciated that the particular configurations described aboveare by way of example only and are not meant to be limiting.

In a possible embodiment, after the instant message is generated, thedirect device uses an already established connection with an instantmessage server and sends the instant message to the instant messageserver to be delivered to the user's DVR (Step 324.) In another possibleembodiment, the direct device opens a new connection to the instantmessage server and sends the instant message to the instant messageserver to be delivered to the user's DVR (Step 324.) In a possibleembodiment, after the instant message is sent to the instant messageserver, the direct device closes the connection to the instant messageserver.

In a possible embodiment, the user's DVR maintains a connection to theinstant message server at all times and receives the instant messageoriginally sent by the direct device via the already establishedconnection to the instant message server.

In a possible embodiment, the direct device or the instant messageserver retries sending the instant message to the user's DVR until thedelivery is successful. In a possible embodiment, the direct device orthe instant message server is notified when the instant message has beensuccessfully delivered to the user's DVR. For example, the direct deviceor the instant message server may receive an instant message from theuser's DVR indicating that the delivery of the instant message wassuccessful. In another possible embodiment, the direct device or theinstant message server stores a copy of the instant message or storesrelated data that may be used for generating a new instant message fordelivery to the user's DVR. Then, when delivery of the instant messagefails, the direct device or the instant message server may send anotherinstant message by using the stored copy or the newly generated instantmessage. For example, when after a specified length of time the directdevice or the instant message server does not receive notification thatthe delivery of the instant message was successful, the copy of theinstant message or the newly generated instant message is subsequentlysent for delivery to the user's DVR. In another possible embodiment, thedirect device or the instant message server tries to resend the instantmessage or the newly generated instant message on a periodic basis untila notification of successful delivery is received or until a specifiedretry limit is reached. For example, the direct device or the instantmessage server may resend the instant message every second. As anotherexample, the direct device or the instant message server may try toresend the instant message 20 times, after which the process thatretries sending the instant message terminates. In another possibleembodiment, when the retry limit is reached, the direct device receivesa notification message indicating that the attempt to deliver theinstant message failed. In a possible embodiment, when the retry limitis reached, the DVR UI displays on the display of the direct device, amessage indicating that the delivery failed or that the user's requestfor the programming event failed. For example, the user's DVR UI maydisplay a message indicating that the attempt to add the season passfailed. In another possible embodiment, when the instant message cannotbe delivered to the user's DVR (e.g., the user's DVR connection to theinstant message server has been dropped), the instant message isdiscarded.

In a possible embodiment, after receiving the instant message containingprogramming event data, such as adding the season pass, the user's DVRperforms the appropriate operation, such as adding the season pass, asif the user had entered the command at the user's DVR. Data reflectingthe programming event is stored in storage 164A/164B. Then, storage 106of service provider 104 is updated with the information stored in164A/164B, including, for example, the added season pass from theexample, via any of the synchronization processes described above.

Scalability and Robustness

In a possible embodiment, the DVR attempts to maintain an SSL connectionwith an XMPP server at all times, reconnecting whenever the connectionis dropped. Because the DVR maintains the SSL connection with the XMPPserver, the DVR has the capability to use instant messaging at alltimes, except during those short intervals when the connection istemporarily dropped. For example, the DVR may employ an alreadyestablished connection with the XMPP server to perform thesynchronization with the service provider. Thus, the DVR using theestablished connection to perform synchronization provides scalability.

In another embodiment, one or more XMPP servers are configured not tostore messages that are sent to any of the one or more XMPP servers. Forexample, an XMPP server receives an XMPP message and passes the XMPPmessage on to a recipient, such as the DVR, without using additionalXMPP server resources for storing the message. Because the one or moreXMPP servers may not need to use additional resources to store XMPPmessages, more XMPP server resources may be used at a given time forprocessing more messages, thus providing greater scalability.

In a possible embodiment, DVR/service provider synchronization viainstant messaging is robust because the DVR and service providerautomatically reconnect after any connection failures during thesynchronization process.

In another embodiment, DVR/service provider synchronization is renderedrobust by a configuration that uses a combination of DVR/serviceprovider synchronization by polling and DVR/service providersynchronization by instant messaging. For example, an administrator mayset DVR/service provider synchronization by polling to operate everytwenty-four hours, while DVR/service provider synchronization by instantmessaging is operable as well. The combination of synchronization bypolling and synchronization by instant messaging renders a robustsynchronization feature. For example, suppose that an XMPP servercrashes at the time that the XMPP server is attempting to send a messageto a DVR, e.g., a request to synchronize, and that the crash causes thesending of the message to fail. In a possible embodiment, the DVR may beupdated from the synchronization by the polling process, possibly at alater time. Thus, synchronization is successful and robust even in acase, which may be rare, when an XMPP message is lost.

Hardware Overview

FIG. 4 is a block diagram that illustrates a computer system 400 uponwhich a possible embodiment of the invention may be implemented.Computer system 400 includes a bus 402 or other communication mechanismfor communicating information, and a processor 404 coupled with bus 402for processing information. Computer system 400 also includes a mainmemory 406, such as a random access memory (“RAM”) or other dynamicstorage device, coupled to bus 402 for storing information andinstructions to be executed by processor 404. Main memory 406 also maybe used for storing temporary variables or other intermediateinformation during execution of instructions to be executed by processor404. Computer system 400 further includes a read only memory (“ROM”) 408or other static storage device coupled to bus 402 for storing staticinformation and instructions for processor 404. A storage device 410,such as a magnetic disk or optical disk, is provided and coupled to bus402 for storing information and instructions.

Computer system 400 may be coupled via bus 402 to a display 412, such asa cathode ray tube (“CRT”), for displaying information to a computeruser. An input device 414, including alphanumeric and other keys, iscoupled to bus 402 for communicating information and command selectionsto processor 404. Another type of user input device is cursor control416, such as a mouse, trackball, stylus, or cursor direction keys forcommunicating direction information and command selections to processor404 and for controlling cursor movement on display 412. This inputdevice typically has two degrees of freedom in two axes, a first axis(e.g., x) and a second axis (e.g., y), that allows the device to specifypositions in a plane.

The invention is related to the use of computer system 400 for selectinga frame of a multi-frame video program for display in accordance with aselected trick play mode of a DVR. According to a possible embodiment ofthe invention, selecting a frame of a multi-frame video program fordisplay in accordance with a selected trick play mode of a DVR isprovided by computer system 400 in response to processor 404 executingone or more sequences of one or more instructions contained in mainmemory 406. Such instructions may be read into main memory 406 fromanother computer-readable medium, such as storage device 410. Executionof the sequences of instructions contained in main memory 406 causesprocessor 404 to perform the process steps described herein. Inalternative embodiments, hard-wired circuitry may be used in place of orin combination with software instructions to implement the invention.Thus, embodiments of the invention are not limited to any specificcombination of hardware circuitry and software.

The term “computer-readable medium” as used herein refers to any mediumthat participates in providing instructions to processor 404 forexecution. Such a medium may take many forms, including but not limitedto, non-volatile media, volatile media, and transmission media.Non-volatile media includes, for example, optical or magnetic disks,such as storage device 410. Volatile media includes dynamic memory, suchas main memory 406. Transmission media includes coaxial cables, copperwire and fiber optics, including the wires that comprise bus 402.Transmission media can also take the form of acoustic or light waves,such as those generated during radio wave and infrared datacommunications.

Common forms of computer-readable media include, for example, a floppydisk, a flexible disk, hard disk, magnetic tape, or any other magneticmedium, a CD-ROM, any other optical medium, punchcards, papertape, anyother physical medium with patterns of holes, a RAM, a PROM, and EPROM,a FLASH-EPROM, or any other memory chip or cartridge.

Various forms of computer readable media may be involved in carrying oneor more sequences of one or more instructions to processor 404 forexecution. For example, the instructions may initially be carried on amagnetic disk of a remote computer. The remote computer can load theinstructions into its dynamic memory and send the instructions over atelephone line using a modem. A modem local to computer system 400 canreceive the data on the telephone line and use an infrared transmitterto convert the data to an infrared signal. An infrared detector canreceive the data carried in the infrared signal and appropriatecircuitry can place the data on bus 402. Bus 402 carries the data tomain memory 406, from which processor 404 retrieves and executes theinstructions. The instructions received by main memory 406 mayoptionally be stored on storage device 410 either before or afterexecution by processor 404.

Computer system 400 also includes a communication interface 418 coupledto bus 402. Communication interface 418 provides a two-way datacommunication coupling to a network link 420 that is connected to alocal network 422. For example, communication interface 418 may be anintegrated services digital network (“ISDN”) card or a modem to providea data communication connection to a corresponding type of telephoneline. As another example, communication interface 418 may be a localarea network (“LAN”) card to provide a data communication connection toa compatible LAN. Wireless links may also be implemented. In any suchimplementation, communication interface 418 sends and receiveselectrical, electromagnetic or optical signals that carry digital datastreams representing various types of information.

Network link 420 typically provides data communication through one ormore networks to other data devices. For example, network link 420 mayprovide a connection through local network 422 to a host computer 424 orto data equipment operated by an Internet Service Provider (“ISP”) 426.ISP 426 in turn provides data communication services through the worldwide packet data communication network now commonly referred to as the“Internet” 428. Local network 422 and Internet 428 both use electrical,electromagnetic or optical signals that carry digital data streams. Thesignals through the various networks and the signals on network link 420and through communication interface 418, which carry the digital data toand from computer system 400, are exemplary forms of carrier wavestransporting the information.

Computer system 400 can send messages and receive data, includingprogram code, through the network(s), network link 420 and communicationinterface 418. In the Internet example, a server 430 might transmit arequested code for an application program through Internet 428, ISP 426,local network 422 and communication interface 418.

The received code may be executed by processor 404 as it is received,and/or stored in storage device 410, or other non-volatile storage forlater execution. In this manner, computer system 400 may obtainapplication code in the form of a carrier wave.

In the foregoing specification, the invention has been described withreference to specific embodiments thereof. It will, however, be evidentthat various modifications and changes may be made thereto withoutdeparting from the broader spirit and scope of the invention. Thespecification and drawings are, accordingly, to be regarded in anillustrative rather than a restrictive sense.

1-27. (canceled)
 28. A method, comprising: receiving, from a device, arequest to add media content to a recording device; in response toreceiving the request, generating, by a server, an electroniccommunication that causes the recording device to add the media content;transmitting, by the server, the electronic communication to therecording device, by opening an authorized connection between the serverand the recording device; in response to the opening of the authorizedconnection and after a specified length of time from the sending of theelectronic communication, determining at the server, whether anotification was received during the specified length of time, whereinthe notification indicates the media content has been added to therecording device; and responsive to determining the notification was notreceived during the specified length of time, resending, by the server,the electronic communication to the recording device.
 29. The method asrecited in claim 28, wherein the electronic communication comprisescredentials of the device for authorization to the server.
 30. Themethod as recited in claim 28, further comprising: opening, from theserver, a connection with the device, prior to the server transmittingthe electronic communication for delivery to the recording device. 31.The method as recited in claim 28, further comprising: receiving, by theserver, a notification message when the delivery is successful.
 32. Themethod as recited in claim 28, further comprising: resending, by theserver, the electronic communication until the delivery is successful oruntil a retry limit is reached.
 33. The method as recited in claim 32,wherein the electronic communication is resent on a periodic basis. 34.The method as recited in claim 32, further comprising: in response tothe retry limit being reached, causing the device to receive anotification message indicating that the delivery failed.
 35. The methodas recited in claim 32, further comprising: in response to the retrylimit being reached, causing to be displayed on a display of the device,a message indicating that the programming event failed.
 36. The methodas recited in claim 28, wherein the device is any of: a personalcomputer, a portable device, or a server.
 37. A non-transitorycomputer-readable storage medium storing instructions, which whenexecuted by one or more processors, causes the one or more processors tocarry out the steps of: receiving, from a device, a request to add mediacontent to a recording device; in response to receiving the request,generating, by a server, an electronic communication that causes therecording device to add the media content; transmitting, by the server,the electronic communication to the recording device, by opening anauthorized connection between the server and the recording device; inresponse to the opening of the authorized connection and after aspecified length of time from the sending of the electroniccommunication, determining at the server, whether a notification wasreceived during the specified length of time, wherein the notificationindicates the media content has been added to the recording device; andresponsive to determining the notification was not received during thespecified length of time, resending, by the server, the electroniccommunication to the recording device.
 38. The non-transitorycomputer-readable storage medium as recited in claim 37, wherein theelectronic communication comprises credentials of the device forauthorization to the server.
 39. The non-transitory computer-readablestorage medium as recited in claim 37, wherein the instructions furthercomprise instructions for: opening, by the device, a connection with theserver, prior to the server sends the electronic communication fordelivery to the recording device.
 40. The non-transitorycomputer-readable storage medium as recited in claim 37, wherein theinstructions further comprise instructions for: receiving, by the deviceor the server, a notification message when the delivery is successful.41. The non-transitory computer-readable storage medium as recited inclaim 37, wherein the instructions further comprise instructions for:resending, by the device or the server, the electronic communicationuntil the delivery is successful or until a retry limit is reached. 42.The non-transitory computer-readable storage medium as recited in claim41, wherein the instructions further comprise instructions for resendingthe electronic communication on a periodic basis.
 43. The non-transitorycomputer-readable storage medium as recited in claim 41, wherein theinstructions further comprise instructions for: receiving, by thedevice, a notification message indicating that the delivery failed, inresponse to the retry limit being reached.
 44. The non-transitorycomputer-readable storage medium as recited in claim 41, wherein theinstructions further comprise instructions for: displaying on a displayof the device, a message indicating that the programming event failed,in response to the retry limit being reached.
 45. The non-transitorycomputer-readable storage medium as recited in claim 37, wherein thedevice is any of: a personal computer, a portable device, or a server.46. A system comprising: a receiving module, at least partly implementedin hardware, that receives at a device, a command to add multimediacontent to record on a recording device; an electronic communicationgeneration module, at least partly implemented in hardware, thatgenerates, by the device, an electronic communication for delivery tothe recording device, the electronic communication containing data thatcauses the recording device to add the multimedia content; a sendingmodule, at least partly implemented in hardware, that sends, by thedevice, the electronic communication for delivery to the recordingdevice via an server to open a connection between the device and theserver, the electronic communication including credentials of the devicefor authorization to the server; a determination module, at least partlyimplemented in hardware, that after a specified length of time from thesending of the electronic communication, determines, by the device,whether a notification message was received from the recording deviceduring the specified length of time, the notification message indicatingwhether the recording device has received the electronic communicationto add the multimedia content, and responsive to determining thenotification message was not received during the specified length oftime, resending the electronic communication.
 47. The system as recitedin claim 46, wherein the electronic communication comprises credentialsof the device for authorization to the server.
 48. The system as recitedin claim 46, further comprising: a connecting module, at least partlyimplemented in hardware, that opens, by the device, a connection to theserver, prior to the server sends the electronic communication fordelivery to the recording device.
 49. The system as recited in claim 46,further comprising: a notification receiving module, at least partlyimplemented in hardware, that receives by the device or the server, anotification message when the delivery is successful.
 50. The system asrecited in claim 46, further comprising: a resending module, at leastpartly implemented in hardware, that resends, by the device or theserver, the electronic communication until the delivery is successful oruntil a retry limit is reached.
 51. The system as recited in claim 50,wherein the electronic communication is resent on a periodic basis. 52.The system as recited in claim 50, further comprising: a notificationreceiving module, at least partly implemented in hardware, that receivesby the device a notification message indicating that the deliveryfailed, in response to the retry limit being reached.
 53. The system asrecited in claim 50, further comprising: a display of the device thatdisplays a message indicating that the programming event failed, inresponse to the retry limit being reached.
 54. The system as recited inclaim 46, wherein the device is any of: a personal computer, a portabledevice, or a server.